Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0155

reference: 722-tree-1
name: 0155
tree-preservation-order: undefined
722-tpo-1
uprn
address-text
point: POINT (-0.989752 50.867647)
geometry: MULTIPOLYGON (((-0.989653 50.867637,-0.989657 50.867656,-0.989671 50.867674,-0.989693 50.867688,-0.989720 50.867697,-0.989751 50.867701,-0.989782 50.867698,-0.989809 50.867689,-0.989832 50.867675,-0.989846 50.867658,-0.989852 50.867638,-0.989847 50.867619,-0.989833 50.867601,-0.989812 50.867587,-0.989784 50.867578,-0.989753 50.867575,-0.989723 50.867578,-0.989695 50.867586,-0.989672 50.867600,-0.989658 50.867617,-0.989653 50.867637)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL